home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Tools & Utilities
/
Collection of Tools and Utilities.iso
/
olrdrs
/
jh3b1of4.zip
/
WHATSNEW.DOC
< prev
Wrap
Text File
|
1993-03-01
|
6KB
|
132 lines
John Hancock 3.0B
-----------------
Entire Work (c) 1992-1993 The Silicon Frog, Inc.
===JH Release 3.0B====================================================
= =
= JH3 Release 3.0B is functionally identical to release 3.0A. The =
= 3.0A JH3A3OF4.ZIP distribution file was missing the .SH2 show =
= files, and the JH3A4OF4.ZIP distribution file was missing the =
= JH3A4OF4.DOC file. No new files were added to release 3.0A to =
= produce release 3.0B. This was a very silly batch file error =
= which the management of the Silicon Frog, Inc., deeply regrets. =
= Thanks to Bob Predaina, a.k.a. Doctor Bob, for finding and =
= reporting the error. =
= =
======================================================================
Upgrade release 3.0A of John Hancock introduces new JH3 features
as well as JH3AUTO, a brand new program which selects taglines
automatically. For information on JH3AUTO, see JH3AUTO.TXT.
PKZIP Version 2.04E
-------------------
PKZIP version 2.04E was used to create the JH3A distribution files;
version 2.04 of PKUNZIP is required to uncompress these files. I know,
it's silly to tell you about this since you won't be able to see it
unless you used PKUNZIP 2.04 or later to uncompress this file. So it
goes.
Release 3.0A Changes
--------------------
Two changes were made to JH 3.0 to yield release 3.0A.
1. JH3.EXE will now accept a command-line tagfile name.
-------------------------------------------------------
You may now specify a tagfile name in the JH3 command line.
To use this feature, start JH3 with the following command
line:
JH3 TAGFILE[.TAG]
If the .TAG extension is not specified, it is assumed. The
TAGFILE file must be in the JH3 tagfile directory specified
in JH3CFG, PreFlight Checklist screen.
Specifying a starting tagfile name in the JH3 command line
supersedes JH3 file loading options defined in the JH3CFG
PreFlight Checklist screen: JH.TAG autoload and Stash
detect. It also overrides the loading of the last-used
tagfile (JH3's default mode if JH.TAG Autoload and Stash
detect are OFF).
This feature was added to provide compatibility and consistency
with release 2.0 of John Hancock. Some JH2 users used
different tagfiles based on some logical decisions, and this new
feature allows them to use the same command line and batch files
that were used with the earlier release of the program.
2. JH3 now allows a /CGA parameter to force 80x25 operation.
------------------------------------------------------------
This feature was added to correct a problem which was reported
by a Desqview(tm) user. Under DV, JH3 receives misleading
information on the size of the text screen, and will access
video memory which physically does not exist. In most cases,
using the JH3 screensiZe command corrects the problem. In
some other cases, JH3 may cause an additional text line to be
added or removed from other existing DV windows active at the
same time.
To start JH3 in "forced" CGA mode, use the following command
line:
JH3 /CGA
The new /CGA parameter forces JH3 to operate as if the video
adapter was a Color Graphics Adapter (CGA), and forces the
physical screen size to a fixed 80 columns by 25 rows,
regardless of the video adapter capabilities or of the actual
screen size in effect, or that reported by Desqview.
In forced CGA mode, JH3 will not observe EGA or VGA color palette
settings -- although the JH3CFG Crayola(tm) Box will allow you to
define or use E/VGA palettes or Gallery files, physical screen
colors are limited to the 16 base colors available on the CGA.
As a result, using /CGA on a E/VGA adapter may yield screen colors
that are different from those shown in JH3CFG. To eliminate this
problem, load the JH3 default gallery file (or use JH3's default
colors) and do NOT use the Crayola box palette to alter base color
hues.
Clarification: JH3 Reminder Screens
-----------------------------------
If you have not registered JH3, the program will start displaying
reminder screens after 30 days and if you have used the program
250 or more times. The JH3 documentation states that you must
completely re-install JH3 in order to get another 30-day trial
of the program.
To re-install JH3, you must erase ALL existing JH3 files, and
you must also remove the JH3 environment variable. In most cases,
INSTALL will refuse to operate if it finds JH3 files in the current
directory or in the tagfile directory.
If you did NOT remove all JH3-related files, INSTALL may decide to
operate without warning, but it will realize that this is not an
original installation. In such cases, INSTALL sets the installation
date and the program use count to much higher starting values. As a
result, you will not enjoy a full 30-day evaluation of the program.
If you re-installed JH3 and start receiving reminder messages much
sooner than expected, this is NOT a program bug -- you simply failed
to delete some of JH3's files, the INSTALL program found them on
your disk, and acted as described above.
The only two known solutions are to register JH3 or go through another
complete re-installation of the program.
If you attempt to defeat or circumvent the start date or use count
feature and JH3 detects it, the starting date will be set immediately
to 31 days in the past and the use cout will be set to 500, which
will yield 15-second reminder messages each time you use JH3. The
only way to correct this undesirable condition is to completely
re-install the program.
Dan Moore
February 1993